Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊
| Attribute | Value |
|---|---|
| Connector ID | RubrikSecurityCloudAzureFunctions |
| Publisher | Rubrik, Inc |
| Used in Solutions | RubrikSecurityCloud |
| Collection Method | Azure Function |
| Connector Definition Files | RubrikWebhookEvents_FunctionApp.json |
| Ingestion API | HTTP Data Collector API — Azure Function code uses SharedKey/HTTP Data Collector API |
| Custom Log V1 Tables | Yes 🔶 — ingests into tables with type-suffixed columns |
The Rubrik Security Cloud data connector enables security operations teams to integrate insights from Rubrik's Data Observability services into Microsoft Sentinel. The insights include identification of anomalous filesystem behavior associated with ransomware and mass deletion, assess the blast radius of a ransomware attack, and sensitive data operators to prioritize and more rapidly investigate potential incidents.
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
Rubrik_Anomaly_Data_CL 🔶 |
? | ✓ | ? |
Rubrik_Events_Data_CL 🔶 |
? | ✓ | ? |
Rubrik_Ransomware_Data_CL 🔶 |
? | ✓ | ? |
Rubrik_ThreatHunt_Data_CL 🔶 |
? | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions: - Workspace (Workspace): read and write permissions on the workspace are required. - Keys (Workspace): read permissions to shared keys for the workspace are required. See the documentation to learn more about workspace keys.
Custom Permissions: - Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. See the documentation to learn more about Azure Functions.
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
NOTE: This connector uses Azure Functions to connect to the Rubrik webhook which push its logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Functions pricing page for details.
(Optional Step) Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. Follow these instructions to use Azure Key Vault with an Azure Function App.
STEP 1 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function
IMPORTANT: Before deploying the Rubrik Microsoft Sentinel data connector, have the Workspace ID and Workspace Primary Key (can be copied from the following) readily available.. - Workspace ID:
WorkspaceIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel. - Primary Key:PrimaryKeyNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
2. Option 1 - Azure Resource Manager (ARM) Template
Use this method for automated deployment of the Rubrik connector.
Click the Deploy to Azure button below.
2. Select the preferred Subscription, Resource Group and Location.
3. Enter the below information :
Function Name
Workspace ID
Workspace Key
AnomaliesTableName
RansomwareAnalysisTableName
ThreatHuntsTableName
EventsTableName
LogLevel
Mark the checkbox labeled I agree to the terms and conditions stated above.
3. Option 2 - Manual Deployment of Azure Functions
Use the following step-by-step instructions to deploy the Rubrik Microsoft Sentinel data connector manually with Azure Functions (Deployment via Visual Studio Code).
1. Deploy a Function App
NOTE: You will need to prepare VS code for Azure function development.
Provide the following information at the prompts:
a. Select folder: Choose a folder from your workspace or browse to one that contains your function app.
b. Select Subscription: Choose the subscription to use.
c. Select Create new Function App in Azure (Don't choose the Advanced option)
d. Enter a globally unique name for the function app: Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (e.g. RubrikXXXXX).
e. Select a runtime: Choose Python 3.8 or above.
f. Select a location for new resources. For better performance and lower costs choose the same region where Microsoft Sentinel is located.
Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.
2. Configure the Function App
Post Deployment steps
7. 1) Get the Function app endpoint
8. 2) Add a webhook in RubrikSecurityCloud to send data to Microsoft Sentinel.
Follow the Rubrik User Guide instructions to Add a Webhook to begin receiving event information
1. Select the Microsoft Sentinel as the webhook Provider
2. Enter the desired Webhook name
3. Enter the URL part from copied Function-url as the webhook URL endpoint and replace {functionname} with "RubrikAnomalyOrchestrator", for the Rubrik Microsoft Sentinel Solution
4. Select the EventType as Anomaly
5. Select the following severity levels: Critical, Warning, Informational
6. Choose multiple log types, if desired, when running "RubrikEventsOrchestrator"
7. Repeat the same steps to add webhooks for Anomaly Detection Analysis, Threat Hunt and Other Events.
NOTE: while adding webhooks for Anomaly Detection Analysis, Threat Hunt and Other Events, replace {functionname} with "RubrikRansomwareOrchestrator", "RubrikThreatHuntOrchestrator" and "RubrikEventsOrchestrator" respectively in copied function-url.
Now we are done with the rubrik Webhook configuration. Once the webhook events triggered , you should be able to see the Anomaly, Anomaly Detection Analysis, Threat Hunt events and Other Events from the Rubrik into respective LogAnalytics workspace table called "Rubrik_Anomaly_Data_CL", "Rubrik_Ransomware_Data_CL", "Rubrik_ThreatHunt_Data_CL", and "Rubrik_Events_Data_CL".
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊